Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdd0f01a28adc1e5ee417e92f086faf5438954a400b4f58baea0ed8b36ae32aa

Tx prefix hash: ef8897c78c27c5cc1062dbff04cf461db2c6646ffab305e69f6cced21f351353
Tx public key: 5a48e23a4c1394e12b91b526cf51c70bb9804251a0db06559cdc7df88a3aa173
Timestamp: 1740271665 Timestamp [UCT]: 2025-02-23 00:47:45 Age [y:d:h:m:s]: 00:227:06:58:34
Block: 1225147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160156 RingCT/type: yes/0
Extra: 015a48e23a4c1394e12b91b526cf51c70bb9804251a0db06559cdc7df88a3aa173021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d87f3f060aef159029f12e1b5f401a6c430bf5983e76d37b3f2e7114b72c423 0.600000000000 1712012 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": 1225157, "vin": [ { "gen": { "height": 1225147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d87f3f060aef159029f12e1b5f401a6c430bf5983e76d37b3f2e7114b72c423" } } ], "extra": [ 1, 90, 72, 226, 58, 76, 19, 148, 225, 43, 145, 181, 38, 207, 81, 199, 11, 185, 128, 66, 81, 160, 219, 6, 85, 156, 220, 125, 248, 138, 58, 161, 115, 2, 17, 0, 0, 0, 5, 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