Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b1b05812c56a4ace0ad526d8215979ecf4bebc20faabb8febef3be03d604f672

Tx prefix hash: d0f62f6ca0a2013fd8ac0cc6d330c57fe585b4373cdcc40c3e33e9bfac5ff922
Tx public key: 691c882c97f318356ccebbc21421683cbfa129ab24f9a1ec7e1ff0b4b7e65f08
Timestamp: 1718070256 Timestamp [UCT]: 2024-06-11 01:44:16 Age [y:d:h:m:s]: 00:174:18:18:15
Block: 1041563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125083 RingCT/type: yes/0
Extra: 01691c882c97f318356ccebbc21421683cbfa129ab24f9a1ec7e1ff0b4b7e65f08021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbf6c219675bf55b440facaeb82a9063f621827b7eacd44fb3565debb8be0c21 0.600000000000 1510268 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1041573, "vin": [ { "gen": { "height": 1041563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbf6c219675bf55b440facaeb82a9063f621827b7eacd44fb3565debb8be0c21" } } ], "extra": [ 1, 105, 28, 136, 44, 151, 243, 24, 53, 108, 206, 187, 194, 20, 33, 104, 60, 191, 161, 41, 171, 36, 249, 161, 236, 126, 31, 240, 180, 183, 230, 95, 8, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8