Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b81766a5ac4b5c3f9f9ea6abd8f62ea559d85e4a1c02480e6002feacb34e7b47

Tx prefix hash: cbf67a69d28a6178371671679071bcdda355a1472e2c7ecf0ed37792e222625e
Tx public key: 44883f8921d15c578f726ce637d90a13d4ce74e3dd82b699ffbfd6168d4a27ad
Timestamp: 1733100223 Timestamp [UCT]: 2024-12-02 00:43:43 Age [y:d:h:m:s]: 00:121:04:45:14
Block: 1166066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86410 RingCT/type: yes/0
Extra: 0144883f8921d15c578f726ce637d90a13d4ce74e3dd82b699ffbfd6168d4a27ad02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a286ee85e3923d9ee717b43e85eae9eeac8d6ba6dfe6ff8fe515b86fbaa4a48a 0.600000000000 1651743 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": 1166076, "vin": [ { "gen": { "height": 1166066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a286ee85e3923d9ee717b43e85eae9eeac8d6ba6dfe6ff8fe515b86fbaa4a48a" } } ], "extra": [ 1, 68, 136, 63, 137, 33, 209, 92, 87, 143, 114, 108, 230, 55, 217, 10, 19, 212, 206, 116, 227, 221, 130, 182, 153, 255, 191, 214, 22, 141, 74, 39, 173, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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