Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d348fa3e78132cf40c7af98ccf3230811b11d8a8a452214896e36f1016f136

Tx prefix hash: c5105a9dd9c8b4a3258f7402af2be3b7dfd2a27743ed494ecae9119a562a71f5
Tx public key: 9b2a54bd5429d12a48f073cad4a206a755ead5dd4be491fae88fcbb1a54ae5a4
Timestamp: 1578151564 Timestamp [UCT]: 2020-01-04 15:26:04 Age [y:d:h:m:s]: 05:036:20:20:18
Block: 38616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176151 RingCT/type: yes/0
Extra: 019b2a54bd5429d12a48f073cad4a206a755ead5dd4be491fae88fcbb1a54ae5a402110000000f4943cd9f000000000000000000

1 output(s) for total of 457.140828864000 dcy

stealth address amount amount idx
00: ee06038627703cf81374dfa1eb12cfa6ec2d8f49419c22adff961b25505bf4a2 457.140828864000 65969 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": 38626, "vin": [ { "gen": { "height": 38616 } } ], "vout": [ { "amount": 457140828864, "target": { "key": "ee06038627703cf81374dfa1eb12cfa6ec2d8f49419c22adff961b25505bf4a2" } } ], "extra": [ 1, 155, 42, 84, 189, 84, 41, 209, 42, 72, 240, 115, 202, 212, 162, 6, 167, 85, 234, 213, 221, 75, 228, 145, 250, 232, 143, 203, 177, 165, 74, 229, 164, 2, 17, 0, 0, 0, 15, 73, 67, 205, 159, 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