Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0f31dfe58622e7bbc3174fa1e49f11f93c40cd8b6036840a2f9193db1ef15f8

Tx prefix hash: d87c016a68b5bc9619e639b4501dd27085364de162435487fd4cfceeeadd0f61
Tx public key: a4ed856a5aba96d85e217a6d903474a65bf521f47e9e3143b2da9f51f0e76e92
Timestamp: 1711710443 Timestamp [UCT]: 2024-03-29 11:07:23 Age [y:d:h:m:s]: 00:301:12:28:34
Block: 988848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215762 RingCT/type: yes/0
Extra: 01a4ed856a5aba96d85e217a6d903474a65bf521f47e9e3143b2da9f51f0e76e920211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31f0289e94191e2b91319e26332cdd57e784854a0814578c16424b5cb6b15d36 0.600000000000 1449135 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": 988858, "vin": [ { "gen": { "height": 988848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31f0289e94191e2b91319e26332cdd57e784854a0814578c16424b5cb6b15d36" } } ], "extra": [ 1, 164, 237, 133, 106, 90, 186, 150, 216, 94, 33, 122, 109, 144, 52, 116, 166, 91, 245, 33, 244, 126, 158, 49, 67, 178, 218, 159, 81, 240, 231, 110, 146, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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