Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2343dd038c4dce78f1a129fa7562541e7297f1b772a7a68f9fdbc8b1e38d19bd

Tx prefix hash: ff9698b86f37e9e2a43fbf6e4e9a32333d78c366358c333912fc85e86fb8e419
Tx public key: a263f5a8a48cd487a849c0a52851cdccfaa9e761e41d197809a4417a1d33b559
Timestamp: 1722794433 Timestamp [UCT]: 2024-08-04 18:00:33 Age [y:d:h:m:s]: 01:093:19:50:15
Block: 1080716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325519 RingCT/type: yes/0
Extra: 01a263f5a8a48cd487a849c0a52851cdccfaa9e761e41d197809a4417a1d33b55902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af2e71c183d525695a90da538cd44d6d6fca6ee62d0fbb726c65c0838a5adac1 0.600000000000 1554181 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": 1080726, "vin": [ { "gen": { "height": 1080716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af2e71c183d525695a90da538cd44d6d6fca6ee62d0fbb726c65c0838a5adac1" } } ], "extra": [ 1, 162, 99, 245, 168, 164, 140, 212, 135, 168, 73, 192, 165, 40, 81, 205, 204, 250, 169, 231, 97, 228, 29, 25, 120, 9, 164, 65, 122, 29, 51, 181, 89, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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