Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbcb33e40626b2d7b6169808845930e06fd3362b389c28c061314ddd42b5b2ed

Tx prefix hash: 15db74ce6de53408802a1b66c8931f56e3807f784e614ec26c96a0cc1b7b435b
Tx public key: 664556835d17bd1d0567a6196bf306f5f450bea7b5cbdd8e302f3d52e721aea1
Timestamp: 1673467436 Timestamp [UCT]: 2023-01-11 20:03:56 Age [y:d:h:m:s]: 02:134:15:17:26
Block: 672643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 617937 RingCT/type: yes/0
Extra: 01664556835d17bd1d0567a6196bf306f5f450bea7b5cbdd8e302f3d52e721aea102110000000252542ceb000000000000000000

1 output(s) for total of 3.624553103000 dcy

stealth address amount amount idx
00: d344c54895af6131508f273f54c2ef9d78327a04c969679330c760f3042197e1 3.624553103000 1114204 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": 672653, "vin": [ { "gen": { "height": 672643 } } ], "vout": [ { "amount": 3624553103, "target": { "key": "d344c54895af6131508f273f54c2ef9d78327a04c969679330c760f3042197e1" } } ], "extra": [ 1, 102, 69, 86, 131, 93, 23, 189, 29, 5, 103, 166, 25, 107, 243, 6, 245, 244, 80, 190, 167, 181, 203, 221, 142, 48, 47, 61, 82, 231, 33, 174, 161, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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