Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0012125fe7785b59d4c5226885628ba72c6163c7faee159a7fd6fd60274504d2

Tx prefix hash: 4725acec5ef8095964c5ffe2e774fee638c15ca80232853b96f6420e19fd097c
Tx public key: 8df0b6e775efc4ea104cbbb7cd6816a1fd4e8cb9df9b910d7d5d75e99b58f509
Timestamp: 1745718710 Timestamp [UCT]: 2025-04-27 01:51:50 Age [y:d:h:m:s]: 00:014:15:29:06
Block: 1270262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10472 RingCT/type: yes/0
Extra: 018df0b6e775efc4ea104cbbb7cd6816a1fd4e8cb9df9b910d7d5d75e99b58f509021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc964b54e4b60a7c4244b4217774ae45fdeb56a3a82f1850339c1dbe41ee24ee 0.600000000000 1757503 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": 1270272, "vin": [ { "gen": { "height": 1270262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc964b54e4b60a7c4244b4217774ae45fdeb56a3a82f1850339c1dbe41ee24ee" } } ], "extra": [ 1, 141, 240, 182, 231, 117, 239, 196, 234, 16, 76, 187, 183, 205, 104, 22, 161, 253, 78, 140, 185, 223, 155, 145, 13, 125, 93, 117, 233, 155, 88, 245, 9, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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