Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7b983bf99069ed6d1e042905b577c0804b4bb2a9121243e4dfbba41cc7f8b2c

Tx prefix hash: c741ddae1e02e2cf19e4e0288add9738994fb25ae9494cb1f1edd270dd7c879f
Tx public key: d30a5023169a6a436f5abf7bd112f6a17f94e77f393c354e43cb4c0b1733e57f
Timestamp: 1728088770 Timestamp [UCT]: 2024-10-05 00:39:30 Age [y:d:h:m:s]: 00:182:12:55:48
Block: 1124614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130255 RingCT/type: yes/0
Extra: 01d30a5023169a6a436f5abf7bd112f6a17f94e77f393c354e43cb4c0b1733e57f021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f47f3ddfd5c0c88d75127a23b7080f6f02c8983361a99a8e8c91dffccbfe6f8 0.600000000000 1607263 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": 1124624, "vin": [ { "gen": { "height": 1124614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f47f3ddfd5c0c88d75127a23b7080f6f02c8983361a99a8e8c91dffccbfe6f8" } } ], "extra": [ 1, 211, 10, 80, 35, 22, 154, 106, 67, 111, 90, 191, 123, 209, 18, 246, 161, 127, 148, 231, 127, 57, 60, 53, 78, 67, 203, 76, 11, 23, 51, 229, 127, 2, 17, 0, 0, 0, 7, 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