Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3c5f3fa28169c453f2a55fb37674fa85ec2f968b8cf8c215d988ee2cf6317d

Tx prefix hash: c3fb014ef21845a178c225e256246cea30ef117cb814bb34a3637da661aa6aa6
Tx public key: 01bb6da78ea6692ada2d544cbb2e4744224d5c89f3013593d05118c60bd4f5b9
Timestamp: 1705573909 Timestamp [UCT]: 2024-01-18 10:31:49 Age [y:d:h:m:s]: 01:038:18:59:51
Block: 937937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288783 RingCT/type: yes/0
Extra: 0101bb6da78ea6692ada2d544cbb2e4744224d5c89f3013593d05118c60bd4f5b902110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19a5cbfe9902d8832d9776e276017d945f2c16fc3aa2e5a5ad665c252bf873aa 0.600000000000 1396001 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": 937947, "vin": [ { "gen": { "height": 937937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19a5cbfe9902d8832d9776e276017d945f2c16fc3aa2e5a5ad665c252bf873aa" } } ], "extra": [ 1, 1, 187, 109, 167, 142, 166, 105, 42, 218, 45, 84, 76, 187, 46, 71, 68, 34, 77, 92, 137, 243, 1, 53, 147, 208, 81, 24, 198, 11, 212, 245, 185, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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