Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 466877f6be5358d4f07fb14a9dd4fd54c2693112da4c0aa7c11bed157b34ecbf

Tx prefix hash: a4b9808740d55e353d577cda6f75dc757aebcfe69d333feef9bf9a0da35a48db
Tx public key: e4f90ecae6b9566e5554cf4c151d67b306dbfeb544556d98afebd6d2c93f4e20
Timestamp: 1702835831 Timestamp [UCT]: 2023-12-17 17:57:11 Age [y:d:h:m:s]: 01:181:03:35:45
Block: 915258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390545 RingCT/type: yes/0
Extra: 01e4f90ecae6b9566e5554cf4c151d67b306dbfeb544556d98afebd6d2c93f4e20021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8800291f9c078eca9c10a6e81cd46eb41e1af4c03b01c8ee804df5300dbc8d99 0.600000000000 1372648 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": 915268, "vin": [ { "gen": { "height": 915258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8800291f9c078eca9c10a6e81cd46eb41e1af4c03b01c8ee804df5300dbc8d99" } } ], "extra": [ 1, 228, 249, 14, 202, 230, 185, 86, 110, 85, 84, 207, 76, 21, 29, 103, 179, 6, 219, 254, 181, 68, 85, 109, 152, 175, 235, 214, 210, 201, 63, 78, 32, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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