Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b3f9a1d8f91515db04fc69a61d408e30279343b0cfc0d2526a03cf78d3e6f0

Tx prefix hash: 0a22b4203079968f758653160759fc08bb0e52dd7db0fcd80eb9ae5adfbe5824
Tx public key: 3b160ca4f3a1f8cbc3d0d0033ea2b3312c672a6b5dcd91ea3dd50d0f33d2908f
Timestamp: 1734672464 Timestamp [UCT]: 2024-12-20 05:27:44 Age [y:d:h:m:s]: 00:094:13:02:55
Block: 1179108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67324 RingCT/type: yes/0
Extra: 013b160ca4f3a1f8cbc3d0d0033ea2b3312c672a6b5dcd91ea3dd50d0f33d2908f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cc82817ab2436c2455f71e5aaec6a90c9ce45f823f3bfad8719652e9fe38cc3 0.600000000000 1665499 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": 1179118, "vin": [ { "gen": { "height": 1179108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cc82817ab2436c2455f71e5aaec6a90c9ce45f823f3bfad8719652e9fe38cc3" } } ], "extra": [ 1, 59, 22, 12, 164, 243, 161, 248, 203, 195, 208, 208, 3, 62, 162, 179, 49, 44, 103, 42, 107, 93, 205, 145, 234, 61, 213, 13, 15, 51, 210, 144, 143, 2, 17, 0, 0, 0, 2, 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