Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b45a8dccb93947bc84518d75386d85fb788e05684252f841362082ffecdd568

Tx prefix hash: 7a4054e53dd3ec47eb236210e25f9f97b3dad1fd1d44133233aed7aa2c290ce8
Tx public key: d6bbb5a7ff6cd145c0e4093e77a2e631a41fdac672aaccf2e9742ed4a05f6ca2
Timestamp: 1728926181 Timestamp [UCT]: 2024-10-14 17:16:21 Age [y:d:h:m:s]: 00:102:07:14:58
Block: 1131562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73082 RingCT/type: yes/0
Extra: 01d6bbb5a7ff6cd145c0e4093e77a2e631a41fdac672aaccf2e9742ed4a05f6ca2021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bedd453826efcf7bb35195e63f1b67490bdc87239b8538145b66d545b7e9769 0.600000000000 1614465 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": 1131572, "vin": [ { "gen": { "height": 1131562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bedd453826efcf7bb35195e63f1b67490bdc87239b8538145b66d545b7e9769" } } ], "extra": [ 1, 214, 187, 181, 167, 255, 108, 209, 69, 192, 228, 9, 62, 119, 162, 230, 49, 164, 31, 218, 198, 114, 170, 204, 242, 233, 116, 46, 212, 160, 95, 108, 162, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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