Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7a985657778fb2783670ab2239d83dab17c7ea49ab82c9f6bf44194aa8ef47b

Tx prefix hash: d02d97537fb360fa4d77b4cd4856dd77a21ec38a039216cf894d64b76e930b30
Tx public key: 8bf92846660e65b163222d2db4d8e88387b3e910ea7a3e42c8347f2988ba3c0e
Timestamp: 1722296683 Timestamp [UCT]: 2024-07-29 23:44:43 Age [y:d:h:m:s]: 00:231:12:39:02
Block: 1076590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165388 RingCT/type: yes/0
Extra: 018bf92846660e65b163222d2db4d8e88387b3e910ea7a3e42c8347f2988ba3c0e02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3082b9385ea59bdf333b48d58e00b729fed6a437e4b06a28ab41bf7f9f9db23e 0.600000000000 1549129 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": 1076600, "vin": [ { "gen": { "height": 1076590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3082b9385ea59bdf333b48d58e00b729fed6a437e4b06a28ab41bf7f9f9db23e" } } ], "extra": [ 1, 139, 249, 40, 70, 102, 14, 101, 177, 99, 34, 45, 45, 180, 216, 232, 131, 135, 179, 233, 16, 234, 122, 62, 66, 200, 52, 127, 41, 136, 186, 60, 14, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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