Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31198ee11eb2654c036525130759373e858a3b00e7dae94bf06063ea39c6ff7b

Tx prefix hash: 344cc6bc72ec615244995011d428f26ba58d5d7df0d985a5fa515fc8a14a3951
Tx public key: 7e360f6bcb233d8d2032d5df7b96a6db3d5754ab42d64c263f77736b372a5fc5
Timestamp: 1704513167 Timestamp [UCT]: 2024-01-06 03:52:47 Age [y:d:h:m:s]: 01:050:17:51:36
Block: 929134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297361 RingCT/type: yes/0
Extra: 017e360f6bcb233d8d2032d5df7b96a6db3d5754ab42d64c263f77736b372a5fc50211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76857d16cf1fa65350d7f5ba59f2688050c7c5af3542f9b4b89b2bd0a387cad5 0.600000000000 1387002 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": 929144, "vin": [ { "gen": { "height": 929134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76857d16cf1fa65350d7f5ba59f2688050c7c5af3542f9b4b89b2bd0a387cad5" } } ], "extra": [ 1, 126, 54, 15, 107, 203, 35, 61, 141, 32, 50, 213, 223, 123, 150, 166, 219, 61, 87, 84, 171, 66, 214, 76, 38, 63, 119, 115, 107, 55, 42, 95, 197, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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