Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26dba53e4f2fe569c7dea627442ad417056921af0e830818df1804ab5ca52edd

Tx prefix hash: 358cee8169a5d3e5b80003a2df0d528cc5bae01a28dbe99eebf619f8960a9a73
Tx public key: aed2c8fb6ca3ce7a547c583592f6412058d4943d5791b71e4bdc533b7911dfcc
Timestamp: 1736641995 Timestamp [UCT]: 2025-01-12 00:33:15 Age [y:d:h:m:s]: 00:066:21:39:51
Block: 1195380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47615 RingCT/type: yes/0
Extra: 01aed2c8fb6ca3ce7a547c583592f6412058d4943d5791b71e4bdc533b7911dfcc0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f18d6e169f59219286c689d463e6d788c76ed81a47d4c6a4f67545ee2bdb768 0.600000000000 1681969 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": 1195390, "vin": [ { "gen": { "height": 1195380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f18d6e169f59219286c689d463e6d788c76ed81a47d4c6a4f67545ee2bdb768" } } ], "extra": [ 1, 174, 210, 200, 251, 108, 163, 206, 122, 84, 124, 88, 53, 146, 246, 65, 32, 88, 212, 148, 61, 87, 145, 183, 30, 75, 220, 83, 59, 121, 17, 223, 204, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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