Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b279bbf83fbe0cfaa07fb5e440a9dfcac6f736c669b2a00d5d4cf5e78a0d5f8

Tx prefix hash: b067170d5030f58a8f2d2a1226d7a68bff28811b3c042019fbd00b9ce8aeae2a
Tx public key: dde5e1804baab212a27a9f54361c6686abdb6811e5afb1cae699a0d43d109acb
Timestamp: 1721152898 Timestamp [UCT]: 2024-07-16 18:01:38 Age [y:d:h:m:s]: 01:084:20:25:43
Block: 1067137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319081 RingCT/type: yes/0
Extra: 01dde5e1804baab212a27a9f54361c6686abdb6811e5afb1cae699a0d43d109acb02110000000ae914dd15000000000000000000

1 output(s) for total of 0.607790000000 dcy

stealth address amount amount idx
00: b8545f6174964d5da7a9c920e568fb62d5b35379b59a278a79e8e4487fe45b8c 0.607790000000 1537864 of 0

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": 1067147, "vin": [ { "gen": { "height": 1067137 } } ], "vout": [ { "amount": 607790000, "target": { "key": "b8545f6174964d5da7a9c920e568fb62d5b35379b59a278a79e8e4487fe45b8c" } } ], "extra": [ 1, 221, 229, 225, 128, 75, 170, 178, 18, 162, 122, 159, 84, 54, 28, 102, 134, 171, 219, 104, 17, 229, 175, 177, 202, 230, 153, 160, 212, 61, 16, 154, 203, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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