Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c2b016bf93d2d1f9010ce0a64f9e3cc6c2e30df4ca294249d669724956cfb3f

Tx prefix hash: 599a210d655ee174641243d841a12ebc40cf53840c38fcf23769f4e56a07bc35
Tx public key: 6f61b55abf6edc8ddd279838b258dca2317a3f77c9082cce87e57ffffbe14a0e
Timestamp: 1713063575 Timestamp [UCT]: 2024-04-14 02:59:35 Age [y:d:h:m:s]: 01:012:06:30:15
Block: 1000027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269750 RingCT/type: yes/0
Extra: 016f61b55abf6edc8ddd279838b258dca2317a3f77c9082cce87e57ffffbe14a0e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b216b3b6bfc8907e9ec4b0bfe586f97d883ab191faba28625d0b0553ad4f5ac0 0.600000000000 1460517 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": 1000037, "vin": [ { "gen": { "height": 1000027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b216b3b6bfc8907e9ec4b0bfe586f97d883ab191faba28625d0b0553ad4f5ac0" } } ], "extra": [ 1, 111, 97, 181, 90, 191, 110, 220, 141, 221, 39, 152, 56, 178, 88, 220, 162, 49, 122, 63, 119, 201, 8, 44, 206, 135, 229, 127, 255, 251, 225, 74, 14, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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