Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ace441fda3f9d945d70d060e6e5ab7c3d8255c091ce4a9823df8a50e64b7a5

Tx prefix hash: 4b55d8f1f6104a12a523911b8e503fd8974f71bf4f3e8e43cd725477c3d7396c
Tx public key: f2903cfd0d6f8c762693dcf6fdd5841cb7fd5ee904129fe7405eb84d0b72fcf0
Timestamp: 1734503835 Timestamp [UCT]: 2024-12-18 06:37:15 Age [y:d:h:m:s]: 00:109:06:25:25
Block: 1177716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77847 RingCT/type: yes/0
Extra: 01f2903cfd0d6f8c762693dcf6fdd5841cb7fd5ee904129fe7405eb84d0b72fcf00211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 003ec26f5540d4eadbcedf17e0bd00ce2039e65468c44d263d64f75d76e294b6 0.600000000000 1664091 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": 1177726, "vin": [ { "gen": { "height": 1177716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "003ec26f5540d4eadbcedf17e0bd00ce2039e65468c44d263d64f75d76e294b6" } } ], "extra": [ 1, 242, 144, 60, 253, 13, 111, 140, 118, 38, 147, 220, 246, 253, 213, 132, 28, 183, 253, 94, 233, 4, 18, 159, 231, 64, 94, 184, 77, 11, 114, 252, 240, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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