Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9047c38705ba76765267c8281c8cb50c3d4d559617d9a9047aa1c2bce5ddb91b

Tx prefix hash: 01505fa51eb96565b453ff9679c13d223bbd8fc996b5605b2103a069a4014de3
Tx public key: ba85d8710ef7a2c1e013b22c3ce8533dd9a69383d12b4a59efda3b06921ebf2c
Timestamp: 1710529034 Timestamp [UCT]: 2024-03-15 18:57:14 Age [y:d:h:m:s]: 01:009:21:23:32
Block: 979052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268034 RingCT/type: yes/0
Extra: 01ba85d8710ef7a2c1e013b22c3ce8533dd9a69383d12b4a59efda3b06921ebf2c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b93fcbf2dfb6a87ba17480457428376f8909ddd18fc97da70464d4415729e86c 0.600000000000 1439083 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": 979062, "vin": [ { "gen": { "height": 979052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b93fcbf2dfb6a87ba17480457428376f8909ddd18fc97da70464d4415729e86c" } } ], "extra": [ 1, 186, 133, 216, 113, 14, 247, 162, 193, 224, 19, 178, 44, 60, 232, 83, 61, 217, 166, 147, 131, 209, 43, 74, 89, 239, 218, 59, 6, 146, 30, 191, 44, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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