Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97f86ebcbd3db6cb306c3a3d49c1ef50e9ea684f93030c81c3d98a5c75c20a9

Tx prefix hash: 98bbcec9494623a39e8240d60aca54f8dc2d842c43ac8f5f48e5664f112d3adf
Tx public key: ae2a90581488787fcbbd117c98052e51a112fc62eda4db605ced61c4e9b0fb8f
Timestamp: 1725109180 Timestamp [UCT]: 2024-08-31 12:59:40 Age [y:d:h:m:s]: 00:214:18:56:40
Block: 1099910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153358 RingCT/type: yes/0
Extra: 01ae2a90581488787fcbbd117c98052e51a112fc62eda4db605ced61c4e9b0fb8f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 675c66f8c0a8facb5ae9fe4ef6aeed51516751bb8cae10360df17585a2e2d9e8 0.600000000000 1575879 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": 1099920, "vin": [ { "gen": { "height": 1099910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "675c66f8c0a8facb5ae9fe4ef6aeed51516751bb8cae10360df17585a2e2d9e8" } } ], "extra": [ 1, 174, 42, 144, 88, 20, 136, 120, 127, 203, 189, 17, 124, 152, 5, 46, 81, 161, 18, 252, 98, 237, 164, 219, 96, 92, 237, 97, 196, 233, 176, 251, 143, 2, 17, 0, 0, 0, 6, 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