Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68111edbb55d1eb860cd6ee45fc5e56c91aa6cf12e5b189f799912da8e3721cd

Tx prefix hash: 344ec163e3d95a6d948a4225de5fbec4f9e26c2b4a88aa61f3cccf222e49401f
Tx public key: fe476f571e27b291c5bace4f51b0d77a1ba6c9e84a551ba1249f5783beb3e160
Timestamp: 1768007102 Timestamp [UCT]: 2026-01-10 01:05:02 Age [y:d:h:m:s]: 00:017:11:30:11
Block: 1452422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12327 RingCT/type: yes/0
Extra: 01fe476f571e27b291c5bace4f51b0d77a1ba6c9e84a551ba1249f5783beb3e160021100000008215bbf89000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4946fdf1362e0ee048bd8e0011266cfa0439a9ef96929d9e7db6f15b8a55865 0.600000000000 1941446 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": 1452432, "vin": [ { "gen": { "height": 1452422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4946fdf1362e0ee048bd8e0011266cfa0439a9ef96929d9e7db6f15b8a55865" } } ], "extra": [ 1, 254, 71, 111, 87, 30, 39, 178, 145, 197, 186, 206, 79, 81, 176, 215, 122, 27, 166, 201, 232, 74, 85, 27, 161, 36, 159, 87, 131, 190, 179, 225, 96, 2, 17, 0, 0, 0, 8, 33, 91, 191, 137, 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