Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60d35b66dab102f8d8893292057f13b6e09b5c41e877adc1192362e2fb5c70b3

Tx prefix hash: 826fbe09b6e300d2dee9cd63384b4d2e3f7f8f97d4e84b44ec8da6ce10e7ea8e
Tx public key: 64eb73e9a682b209d46305ff045e401495683397f72362326d36eb33f4e590b5
Timestamp: 1702134347 Timestamp [UCT]: 2023-12-09 15:05:47 Age [y:d:h:m:s]: 01:109:23:54:46
Block: 909439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339756 RingCT/type: yes/0
Extra: 0164eb73e9a682b209d46305ff045e401495683397f72362326d36eb33f4e590b50211000000044b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3495da03ec1f0596317f789c47c2c21f10f8b5e2a2980c73e7d85322935e6f9f 0.600000000000 1366526 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": 909449, "vin": [ { "gen": { "height": 909439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3495da03ec1f0596317f789c47c2c21f10f8b5e2a2980c73e7d85322935e6f9f" } } ], "extra": [ 1, 100, 235, 115, 233, 166, 130, 178, 9, 212, 99, 5, 255, 4, 94, 64, 20, 149, 104, 51, 151, 247, 35, 98, 50, 109, 54, 235, 51, 244, 229, 144, 181, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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