Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e077e99e0d06bc9c7ea92b0c1cd4f4fcf63872b81c409b25d625c723441523a

Tx prefix hash: 533c7997d39d9c3abb20c9d9790bbe385b5e5edee4bcdef212daff9731a396b3
Tx public key: bbb2569bd4717cb0cf56e3ad057640dd8df4e578f2d972b360ab16ed78bd3f61
Timestamp: 1707582632 Timestamp [UCT]: 2024-02-10 16:30:32 Age [y:d:h:m:s]: 01:105:02:07:37
Block: 954604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336195 RingCT/type: yes/0
Extra: 01bbb2569bd4717cb0cf56e3ad057640dd8df4e578f2d972b360ab16ed78bd3f610211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc4f36a3e24b2ba0e81c293fccf8273ec796049e1c62c31e4a966bb91dedd520 0.600000000000 1413884 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": 954614, "vin": [ { "gen": { "height": 954604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc4f36a3e24b2ba0e81c293fccf8273ec796049e1c62c31e4a966bb91dedd520" } } ], "extra": [ 1, 187, 178, 86, 155, 212, 113, 124, 176, 207, 86, 227, 173, 5, 118, 64, 221, 141, 244, 229, 120, 242, 217, 114, 179, 96, 171, 22, 237, 120, 189, 63, 97, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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