Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1edf0c4472037e6166ce1db4a44218fdbe1055299a7f4e812a2620307314f8b3

Tx prefix hash: 76bab5534ebe4e8721b3b8a8034f363dbbf1b95f300f6eb971c9fc7c95a88c3c
Tx public key: 29f281403498e73c770e2a7c0a8748fd9799a032e1b3694fe92fe9aa6d80cb33
Timestamp: 1745722047 Timestamp [UCT]: 2025-04-27 02:47:27 Age [y:d:h:m:s]: 00:011:20:29:49
Block: 1270290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8468 RingCT/type: yes/0
Extra: 0129f281403498e73c770e2a7c0a8748fd9799a032e1b3694fe92fe9aa6d80cb3302110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42ecc0c8836933d91bcc5144c446f695e924310ee026c69b570e02192eb4f791 0.600000000000 1757531 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": 1270300, "vin": [ { "gen": { "height": 1270290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42ecc0c8836933d91bcc5144c446f695e924310ee026c69b570e02192eb4f791" } } ], "extra": [ 1, 41, 242, 129, 64, 52, 152, 231, 60, 119, 14, 42, 124, 10, 135, 72, 253, 151, 153, 160, 50, 225, 179, 105, 79, 233, 47, 233, 170, 109, 128, 203, 51, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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