Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfe8e60c4950774ae161775d6726b15e0e388e09df787e3a6265b8d62c75526b

Tx prefix hash: bbbc7bd87b43dc8321e6b45f47440eec9d091487e298350c53308cef628e4d69
Tx public key: ee918898f6febdb90714f8019d4833957c30f5ac8b1dea1cbcffb6275763091f
Timestamp: 1731226242 Timestamp [UCT]: 2024-11-10 08:10:42 Age [y:d:h:m:s]: 00:129:09:59:06
Block: 1150532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92337 RingCT/type: yes/0
Extra: 01ee918898f6febdb90714f8019d4833957c30f5ac8b1dea1cbcffb6275763091f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1ba4b5336eaa33f85b0007ebf238b157d8ab5f588b8a5b87cc9a1909ec7981c 0.600000000000 1635875 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": 1150542, "vin": [ { "gen": { "height": 1150532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1ba4b5336eaa33f85b0007ebf238b157d8ab5f588b8a5b87cc9a1909ec7981c" } } ], "extra": [ 1, 238, 145, 136, 152, 246, 254, 189, 185, 7, 20, 248, 1, 157, 72, 51, 149, 124, 48, 245, 172, 139, 29, 234, 28, 188, 255, 182, 39, 87, 99, 9, 31, 2, 17, 0, 0, 0, 3, 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