Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fb89c3dc0e50803ecbb286f5b1efd9280bc2f5cc90c962a2a32354721b36cc8

Tx prefix hash: 1abb639903778774ea1b3f1b1c87729997a78668ea99393729c31d6172e02cdf
Tx public key: f8063f38afcf328c2900a7fb3cf2b8e51646a1cc05a5203d827b2daa6775e389
Timestamp: 1694491839 Timestamp [UCT]: 2023-09-12 04:10:39 Age [y:d:h:m:s]: 01:066:00:25:37
Block: 846260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308479 RingCT/type: yes/0
Extra: 01f8063f38afcf328c2900a7fb3cf2b8e51646a1cc05a5203d827b2daa6775e389021100000003faf35c9c000000000000000000

1 output(s) for total of 0.963805461000 dcy

stealth address amount amount idx
00: 1accdc357af60a1ca5f2c5c8b087e6e6b64f3e679ba884738b2aeb4e4aef4ab8 0.963805461000 1299710 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": 846270, "vin": [ { "gen": { "height": 846260 } } ], "vout": [ { "amount": 963805461, "target": { "key": "1accdc357af60a1ca5f2c5c8b087e6e6b64f3e679ba884738b2aeb4e4aef4ab8" } } ], "extra": [ 1, 248, 6, 63, 56, 175, 207, 50, 140, 41, 0, 167, 251, 60, 242, 184, 229, 22, 70, 161, 204, 5, 165, 32, 61, 130, 123, 45, 170, 103, 117, 227, 137, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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