Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ce2af39053d3d91cdf632c49e1407059827b215045772f52b8e096befe31a8d

Tx prefix hash: 508d31f515cfb7880a07e25f860ab3244e5d33189722b48a86a8dcd094bdf78b
Tx public key: b03c38721902f94d530616930692ccd35b1235caa14f8f911e19bc469e0ee914
Timestamp: 1698467472 Timestamp [UCT]: 2023-10-28 04:31:12 Age [y:d:h:m:s]: 01:163:14:02:29
Block: 879255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377903 RingCT/type: yes/0
Extra: 01b03c38721902f94d530616930692ccd35b1235caa14f8f911e19bc469e0ee91402110000000de6d27f9c000000000000000000

1 output(s) for total of 0.749312888000 dcy

stealth address amount amount idx
00: d960814c1afcad68ac3e62cea184d130e746d2f44643a0a0a534c65ee9a9aa54 0.749312888000 1334761 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": 879265, "vin": [ { "gen": { "height": 879255 } } ], "vout": [ { "amount": 749312888, "target": { "key": "d960814c1afcad68ac3e62cea184d130e746d2f44643a0a0a534c65ee9a9aa54" } } ], "extra": [ 1, 176, 60, 56, 114, 25, 2, 249, 77, 83, 6, 22, 147, 6, 146, 204, 211, 91, 18, 53, 202, 161, 79, 143, 145, 30, 25, 188, 70, 158, 14, 233, 20, 2, 17, 0, 0, 0, 13, 230, 210, 127, 156, 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