Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f93fbba583f96d1a7b0f961959351f59fa96fcd87bf77308c47338487e2e8c72

Tx prefix hash: 81e70e661dd2ef441cb30162695e897a654bfbdfd9d8177b73458506e869e067
Tx public key: 826aae4616fa2b1a35a267e4e50cdbe800f90c768afab43c3f01ffe3309aa083
Timestamp: 1730829095 Timestamp [UCT]: 2024-11-05 17:51:35 Age [y:d:h:m:s]: 00:018:13:40:50
Block: 1147243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13296 RingCT/type: yes/0
Extra: 01826aae4616fa2b1a35a267e4e50cdbe800f90c768afab43c3f01ffe3309aa08302110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffe233ff5e5ecf2b4ebd3bf7c9c02ddc57c0d7f149d6c5fb688ebe6567d0fe5f 0.600000000000 1631938 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": 1147253, "vin": [ { "gen": { "height": 1147243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffe233ff5e5ecf2b4ebd3bf7c9c02ddc57c0d7f149d6c5fb688ebe6567d0fe5f" } } ], "extra": [ 1, 130, 106, 174, 70, 22, 250, 43, 26, 53, 162, 103, 228, 229, 12, 219, 232, 0, 249, 12, 118, 138, 250, 180, 60, 63, 1, 255, 227, 48, 154, 160, 131, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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