Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db5ae70c8de6c05edafbf3e42f14fcdb95eb93938f0841344dbdcf167eccf997

Tx prefix hash: 4220f233ec7c84bca1595ad11510d18c974b4d15a9cc7a2c6d0b92e1c7d9fd5e
Tx public key: 0ebd92fbe239bf56cf27ef4c7d9a94774354df4ea3667a4a257784c82161615f
Timestamp: 1631475491 Timestamp [UCT]: 2021-09-12 19:38:11 Age [y:d:h:m:s]: 03:074:07:56:36
Block: 332491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 828646 RingCT/type: yes/0
Extra: 010ebd92fbe239bf56cf27ef4c7d9a94774354df4ea3667a4a257784c82161615f021100000019f60c5d7e000000000000000000

1 output(s) for total of 48.564591084000 dcy

stealth address amount amount idx
00: 6ff07c1e5fc02c26c8a7d463e5e6696c321cd7e8cea8b37015c16c0ed57fcc2d 48.564591084000 686560 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": 332501, "vin": [ { "gen": { "height": 332491 } } ], "vout": [ { "amount": 48564591084, "target": { "key": "6ff07c1e5fc02c26c8a7d463e5e6696c321cd7e8cea8b37015c16c0ed57fcc2d" } } ], "extra": [ 1, 14, 189, 146, 251, 226, 57, 191, 86, 207, 39, 239, 76, 125, 154, 148, 119, 67, 84, 223, 78, 163, 102, 122, 74, 37, 119, 132, 200, 33, 97, 97, 95, 2, 17, 0, 0, 0, 25, 246, 12, 93, 126, 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