Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c378ab30a64da5cf8c0ee174939b27a0ce78c8dd25c3a6436c44b274d1d054b

Tx prefix hash: 22f51bea37e1a5a8258dd8894e1b94265743a710952a717ba81aeec531216527
Tx public key: 55b15186ba6f8ea3afe591360328dcb9df1e2a2cc08c3a1c0c1a8b0203a84c55
Timestamp: 1701196400 Timestamp [UCT]: 2023-11-28 18:33:20 Age [y:d:h:m:s]: 00:352:09:11:01
Block: 901656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252321 RingCT/type: yes/0
Extra: 0155b15186ba6f8ea3afe591360328dcb9df1e2a2cc08c3a1c0c1a8b0203a84c5502110000000875e3f0e9000000000000000000

1 output(s) for total of 0.631595981000 dcy

stealth address amount amount idx
00: 6667ce0e0f42bf07b96e8a995d84c264574a3590b1d64956882ec73c32e29a6c 0.631595981000 1358229 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": 901666, "vin": [ { "gen": { "height": 901656 } } ], "vout": [ { "amount": 631595981, "target": { "key": "6667ce0e0f42bf07b96e8a995d84c264574a3590b1d64956882ec73c32e29a6c" } } ], "extra": [ 1, 85, 177, 81, 134, 186, 111, 142, 163, 175, 229, 145, 54, 3, 40, 220, 185, 223, 30, 42, 44, 192, 140, 58, 28, 12, 26, 139, 2, 3, 168, 76, 85, 2, 17, 0, 0, 0, 8, 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