Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f500df63b5f319fd9e007a1182e5eecd592bc2d8983399dd15123023d5ff52b1

Tx prefix hash: 2ab181641e3809c5257b990e1faa43973ea8098f3b3192b216f469026981ece3
Tx public key: a6a71f3083cbba437b401e8345473c013e7603f53c6b6088163b9fa5c495312a
Timestamp: 1672881241 Timestamp [UCT]: 2023-01-05 01:14:01 Age [y:d:h:m:s]: 02:023:11:25:21
Block: 667780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538460 RingCT/type: yes/0
Extra: 01a6a71f3083cbba437b401e8345473c013e7603f53c6b6088163b9fa5c495312a02110000000675e3f0e9000000000000000000

1 output(s) for total of 3.761556694000 dcy

stealth address amount amount idx
00: 458441ae809e54829fe3c17b063c5f5212c31bfd0cef494e9f3fe6d2bf84af6d 3.761556694000 1108999 of 0

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": 667790, "vin": [ { "gen": { "height": 667780 } } ], "vout": [ { "amount": 3761556694, "target": { "key": "458441ae809e54829fe3c17b063c5f5212c31bfd0cef494e9f3fe6d2bf84af6d" } } ], "extra": [ 1, 166, 167, 31, 48, 131, 203, 186, 67, 123, 64, 30, 131, 69, 71, 60, 1, 62, 118, 3, 245, 60, 107, 96, 136, 22, 59, 159, 165, 196, 149, 49, 42, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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