Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb572e1838b96ee2d69764ef4448376d6b1b4a184beb21efb5b9b56814dd192a

Tx prefix hash: 578b71340b7d32366dba881bd1d03b2f5943e3016d590968d3bdae45f2cd6f00
Tx public key: e0a878ff7146fb9b84e1ae3e2a810fe85bcea4aef2d4e9069bb256df29257fba
Timestamp: 1707886357 Timestamp [UCT]: 2024-02-14 04:52:37 Age [y:d:h:m:s]: 01:087:10:20:35
Block: 957119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323553 RingCT/type: yes/0
Extra: 01e0a878ff7146fb9b84e1ae3e2a810fe85bcea4aef2d4e9069bb256df29257fba02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a655e412f51f98a0b01c87b03726ad136881c50e7b4732e04e89470aa25e1e1a 0.600000000000 1416435 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": 957129, "vin": [ { "gen": { "height": 957119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a655e412f51f98a0b01c87b03726ad136881c50e7b4732e04e89470aa25e1e1a" } } ], "extra": [ 1, 224, 168, 120, 255, 113, 70, 251, 155, 132, 225, 174, 62, 42, 129, 15, 232, 91, 206, 164, 174, 242, 212, 233, 6, 155, 178, 86, 223, 41, 37, 127, 186, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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