Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3ce56458a2c35763f720124f1eaea3dcd605be7319ca8a0a0a6760fe11e1ce8

Tx prefix hash: f632cab9b0d0034b7d93af6a00cdb688f3d0bdd6b8974a1d345d391ce12f9810
Tx public key: e9379951679e6845d2a0d2210d81e168fd3dc43e0948f8b8cebf0342365a921f
Timestamp: 1758085963 Timestamp [UCT]: 2025-09-17 05:12:43 Age [y:d:h:m:s]: 00:053:14:30:01
Block: 1370191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38392 RingCT/type: yes/0
Extra: 01e9379951679e6845d2a0d2210d81e168fd3dc43e0948f8b8cebf0342365a921f021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 952a11615a90e5610c5117f4e8b9a6bd2591870b841ce424ce46d536f949d58a 0.600000000000 1858266 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": 1370201, "vin": [ { "gen": { "height": 1370191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "952a11615a90e5610c5117f4e8b9a6bd2591870b841ce424ce46d536f949d58a" } } ], "extra": [ 1, 233, 55, 153, 81, 103, 158, 104, 69, 210, 160, 210, 33, 13, 129, 225, 104, 253, 61, 196, 62, 9, 72, 248, 184, 206, 191, 3, 66, 54, 90, 146, 31, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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