Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 087f261284db4354c484b5703f484e3295320fc687b926350257932c2c1d03cf

Tx prefix hash: 972820f1445b054a28e8efea725952d359c75b57c5adc935ab2f6decfe500c56
Tx public key: cef42e71eca932cf016fbbcb16c4c71715213470abcb5f6d4dec1fd2641dbdc9
Timestamp: 1697296500 Timestamp [UCT]: 2023-10-14 15:15:00 Age [y:d:h:m:s]: 01:169:20:37:21
Block: 869527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382424 RingCT/type: yes/0
Extra: 01cef42e71eca932cf016fbbcb16c4c71715213470abcb5f6d4dec1fd2641dbdc902110000000875e3f0e9000000000000000000

1 output(s) for total of 0.807041967000 dcy

stealth address amount amount idx
00: 74913c74c72aca74bd91e638a4c34271c17a4cf4b336dffc50c7b4b320eb5e1e 0.807041967000 1324374 of 0

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": 869537, "vin": [ { "gen": { "height": 869527 } } ], "vout": [ { "amount": 807041967, "target": { "key": "74913c74c72aca74bd91e638a4c34271c17a4cf4b336dffc50c7b4b320eb5e1e" } } ], "extra": [ 1, 206, 244, 46, 113, 236, 169, 50, 207, 1, 111, 187, 203, 22, 196, 199, 23, 21, 33, 52, 112, 171, 203, 95, 109, 77, 236, 31, 210, 100, 29, 189, 201, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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