Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66be66ccb263d2e03b4b5046eac17e865441fd884a764e3cf87c274df262533c

Tx prefix hash: 93a4298f4be996033c321630a53b3baa48e4b781bf993e510c722f95ff2e30db
Tx public key: f21e2dd45c3caaf1530dbfb7b3b174e70fdc440453ae72159f32a35aa7c0f2fc
Timestamp: 1723874948 Timestamp [UCT]: 2024-08-17 06:09:08 Age [y:d:h:m:s]: 00:236:06:27:30
Block: 1089687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168735 RingCT/type: yes/0
Extra: 01f21e2dd45c3caaf1530dbfb7b3b174e70fdc440453ae72159f32a35aa7c0f2fc02110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 861022f5207ecdbe3ba3b71a82d06f790482d04a3501dabc7a11838651cbf26a 0.600000000000 1564310 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": 1089697, "vin": [ { "gen": { "height": 1089687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "861022f5207ecdbe3ba3b71a82d06f790482d04a3501dabc7a11838651cbf26a" } } ], "extra": [ 1, 242, 30, 45, 212, 92, 60, 170, 241, 83, 13, 191, 183, 179, 177, 116, 231, 15, 220, 68, 4, 83, 174, 114, 21, 159, 50, 163, 90, 167, 192, 242, 252, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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