Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df9d47411be2c6dc686232bf2a7f21f5d79c03fc0f49e89df978850c04ec551e

Tx prefix hash: eef428f24d36327c077009b132234a6522277072d6546aae61719a1f14420e3b
Tx public key: 7b6241da9744b5ac95fb37d221a683d18ac3f6aeb92a87b41278f894988f0b7d
Timestamp: 1741603007 Timestamp [UCT]: 2025-03-10 10:36:47 Age [y:d:h:m:s]: 00:256:05:18:51
Block: 1236203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180840 RingCT/type: yes/0
Extra: 017b6241da9744b5ac95fb37d221a683d18ac3f6aeb92a87b41278f894988f0b7d02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfea6c1eb2de3f5c909b17691e37b1564caba86407b65c92cb8a79090683cefb 0.600000000000 1723148 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": 1236213, "vin": [ { "gen": { "height": 1236203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfea6c1eb2de3f5c909b17691e37b1564caba86407b65c92cb8a79090683cefb" } } ], "extra": [ 1, 123, 98, 65, 218, 151, 68, 181, 172, 149, 251, 55, 210, 33, 166, 131, 209, 138, 195, 246, 174, 185, 42, 135, 180, 18, 120, 248, 148, 152, 143, 11, 125, 2, 17, 0, 0, 0, 11, 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