Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6d68dcc783b0c65d9a61001a640f747852134a87f94524b4cccbdb878acc5ca

Tx prefix hash: c6307d654df60682fd62ea954d7e6107d7e7ec51599af2a03582ca08c0a44c91
Tx public key: 6428a504e5a8563c3f45fb9fbbb2f2594bcf714a661690abe9695ca819abad75
Timestamp: 1711877489 Timestamp [UCT]: 2024-03-31 09:31:29 Age [y:d:h:m:s]: 00:228:14:45:15
Block: 990234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163656 RingCT/type: yes/0
Extra: 016428a504e5a8563c3f45fb9fbbb2f2594bcf714a661690abe9695ca819abad750211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa2febfdfd5b62750fd8b54547959b71a73ee9d2efac2e42f2e3c4ffb9c11015 0.600000000000 1450556 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": 990244, "vin": [ { "gen": { "height": 990234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa2febfdfd5b62750fd8b54547959b71a73ee9d2efac2e42f2e3c4ffb9c11015" } } ], "extra": [ 1, 100, 40, 165, 4, 229, 168, 86, 60, 63, 69, 251, 159, 187, 178, 242, 89, 75, 207, 113, 74, 102, 22, 144, 171, 233, 105, 92, 168, 25, 171, 173, 117, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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