Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fafb12b206e69da3bed5e3c4f80dac0e2717724254ec95eec2deaf6c5f5617cd

Tx prefix hash: cb8e06457b832d13fa7a7bae5245b314d077a04b4076a595503c585fd6422e16
Tx public key: 0a913da6da6f926dfa262061fc37b40c9ee0223a663b5a57a37651bc04446658
Timestamp: 1741730328 Timestamp [UCT]: 2025-03-11 21:58:48 Age [y:d:h:m:s]: 00:325:00:10:40
Block: 1237250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229926 RingCT/type: yes/0
Extra: 010a913da6da6f926dfa262061fc37b40c9ee0223a663b5a57a37651bc04446658021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab52dec4e3903521f8dced44c4dc35cb0f949b9976f3d67b34f0994ecf02e552 0.600000000000 1724205 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": 1237260, "vin": [ { "gen": { "height": 1237250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab52dec4e3903521f8dced44c4dc35cb0f949b9976f3d67b34f0994ecf02e552" } } ], "extra": [ 1, 10, 145, 61, 166, 218, 111, 146, 109, 250, 38, 32, 97, 252, 55, 180, 12, 158, 224, 34, 58, 102, 59, 90, 87, 163, 118, 81, 188, 4, 68, 102, 88, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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