Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83609205cc3a448ab70695ac82d4bd73286e6c25fae33c39d9ce1bfd073cd464

Tx prefix hash: 8d517a7eef8e3ec1851648046a5aa47f659c63b91ea20413c0df3effe92fb0a7
Tx public key: 81775399ae9f8a4943443dc3c47e96f1553e4262aa8be3c9a4ef94a987fe6fe1
Timestamp: 1704613787 Timestamp [UCT]: 2024-01-07 07:49:47 Age [y:d:h:m:s]: 01:137:04:16:03
Block: 929972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359201 RingCT/type: yes/0
Extra: 0181775399ae9f8a4943443dc3c47e96f1553e4262aa8be3c9a4ef94a987fe6fe10211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e03c6776c72c1eddd379b2cf1e1c0ef794462ce15e45554e8eb3e0b285b9bab8 0.600000000000 1387850 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": 929982, "vin": [ { "gen": { "height": 929972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e03c6776c72c1eddd379b2cf1e1c0ef794462ce15e45554e8eb3e0b285b9bab8" } } ], "extra": [ 1, 129, 119, 83, 153, 174, 159, 138, 73, 67, 68, 61, 195, 196, 126, 150, 241, 85, 62, 66, 98, 170, 139, 227, 201, 164, 239, 148, 169, 135, 254, 111, 225, 2, 17, 0, 0, 0, 7, 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