Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f05ab3f42d27836898276e3221ba9ced0782cc043491c2f52b47f5bd27efd994

Tx prefix hash: 96db79788fef27c17b482e236e3db6e68751eb7b964fdabbe4d3828a648dd947
Tx public key: b24b471eb288ddeedd15df986109d54b82d38c4fc45ec67f8fd8e90d45aa2c70
Timestamp: 1673891144 Timestamp [UCT]: 2023-01-16 17:45:44 Age [y:d:h:m:s]: 02:002:04:58:46
Block: 676149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523467 RingCT/type: yes/0
Extra: 01b24b471eb288ddeedd15df986109d54b82d38c4fc45ec67f8fd8e90d45aa2c70021100000002faf35c9c000000000000000000

1 output(s) for total of 3.528885997000 dcy

stealth address amount amount idx
00: 56e9e71639f11a9094c9231411553e1789cb9d6e13c91b5a5a9122e3c58d7b8e 3.528885997000 1117858 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": 676159, "vin": [ { "gen": { "height": 676149 } } ], "vout": [ { "amount": 3528885997, "target": { "key": "56e9e71639f11a9094c9231411553e1789cb9d6e13c91b5a5a9122e3c58d7b8e" } } ], "extra": [ 1, 178, 75, 71, 30, 178, 136, 221, 238, 221, 21, 223, 152, 97, 9, 213, 75, 130, 211, 140, 79, 196, 94, 198, 127, 143, 216, 233, 13, 69, 170, 44, 112, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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