Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 084a49de555cc0e3c3b9038b45c627e253a817b03166eed992b30bcd07fb7b8b

Tx prefix hash: 1dc29db13cdd5d163a9c4e79ba86e4330ee16ff9681ef1dba4f332a9e3d2147d
Tx public key: 6531b2d6ccb80eb6774e1aae4f071a9f3c018c055065b3c8d4f825ae6adb5fe5
Timestamp: 1733974959 Timestamp [UCT]: 2024-12-12 03:42:39 Age [y:d:h:m:s]: 00:103:07:37:42
Block: 1173325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73611 RingCT/type: yes/0
Extra: 016531b2d6ccb80eb6774e1aae4f071a9f3c018c055065b3c8d4f825ae6adb5fe5021100000002a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2566ee2db933545fc978b27bc41cf7efcc865d434ddb68ffdc11f4c02a7ca850 0.600000000000 1659336 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": 1173335, "vin": [ { "gen": { "height": 1173325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2566ee2db933545fc978b27bc41cf7efcc865d434ddb68ffdc11f4c02a7ca850" } } ], "extra": [ 1, 101, 49, 178, 214, 204, 184, 14, 182, 119, 78, 26, 174, 79, 7, 26, 159, 60, 1, 140, 5, 80, 101, 179, 200, 212, 248, 37, 174, 106, 219, 95, 229, 2, 17, 0, 0, 0, 2, 162, 215, 95, 68, 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