Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4db51a63d43891dcbcf0cf7517c04d3d6ee7d00aef07c891b1976160ad4fe05

Tx prefix hash: b8f1fdfeae7eaa61069230fddf74660c9a572c6dcf3764cb723a53cd941d709f
Tx public key: fec7dc6889739be82aea46d4cb0bb0a9fca7d6b613e1364c7c37995a3a4a12ff
Timestamp: 1709977083 Timestamp [UCT]: 2024-03-09 09:38:03 Age [y:d:h:m:s]: 01:024:05:27:20
Block: 974470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278304 RingCT/type: yes/0
Extra: 01fec7dc6889739be82aea46d4cb0bb0a9fca7d6b613e1364c7c37995a3a4a12ff02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f43eb6abb6cbb8d7890948b30add832e33f1b36678b40551f71a1ff43bb671 0.600000000000 1434427 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": 974480, "vin": [ { "gen": { "height": 974470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f43eb6abb6cbb8d7890948b30add832e33f1b36678b40551f71a1ff43bb671" } } ], "extra": [ 1, 254, 199, 220, 104, 137, 115, 155, 232, 42, 234, 70, 212, 203, 11, 176, 169, 252, 167, 214, 182, 19, 225, 54, 76, 124, 55, 153, 90, 58, 74, 18, 255, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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