Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 172d0a6fca6d5a0030c5569580d32be28700ec861cfae4eddf6a047ccd601e44

Tx prefix hash: 87c40ac4a14f4255c7392cb66c678e5033c56e9995a40948b6d4e5cecfdc9ca1
Tx public key: 752074425d12f8a1a47bb550c91fb9f0931a85ec39c6c931cf6ad436e75ba052
Timestamp: 1704035159 Timestamp [UCT]: 2023-12-31 15:05:59 Age [y:d:h:m:s]: 01:173:10:22:57
Block: 925196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384930 RingCT/type: yes/0
Extra: 01752074425d12f8a1a47bb550c91fb9f0931a85ec39c6c931cf6ad436e75ba0520211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b02bfe7671e9162dea4a0f3a6da74ff5ea598c11ede70c47adad1f44dda1bc0a 0.600000000000 1382956 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": 925206, "vin": [ { "gen": { "height": 925196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b02bfe7671e9162dea4a0f3a6da74ff5ea598c11ede70c47adad1f44dda1bc0a" } } ], "extra": [ 1, 117, 32, 116, 66, 93, 18, 248, 161, 164, 123, 181, 80, 201, 31, 185, 240, 147, 26, 133, 236, 57, 198, 201, 49, 207, 106, 212, 54, 231, 91, 160, 82, 2, 17, 0, 0, 0, 6, 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