Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d97c0e06d816825454c6909a1baddfd4486c1efc1b070746883e3a11ab406e8b

Tx prefix hash: 4280df663b987c31976828d2ce5a5c9354d6d251733d7bc911a57f13146c6402
Tx public key: afe934797f627b7d7ea3f8b9430c8a4ac19fa3fc4bded5de525d1f77f7a855e5
Timestamp: 1704499924 Timestamp [UCT]: 2024-01-06 00:12:04 Age [y:d:h:m:s]: 01:092:10:34:11
Block: 929035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327172 RingCT/type: yes/0
Extra: 01afe934797f627b7d7ea3f8b9430c8a4ac19fa3fc4bded5de525d1f77f7a855e50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31cdf13216cfb6edae6fea1618618e05cc4b2da1fe4669b046e5ecb1da427bcc 0.600000000000 1386903 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": 929045, "vin": [ { "gen": { "height": 929035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31cdf13216cfb6edae6fea1618618e05cc4b2da1fe4669b046e5ecb1da427bcc" } } ], "extra": [ 1, 175, 233, 52, 121, 127, 98, 123, 125, 126, 163, 248, 185, 67, 12, 138, 74, 193, 159, 163, 252, 75, 222, 213, 222, 82, 93, 31, 119, 247, 168, 85, 229, 2, 17, 0, 0, 0, 4, 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