Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52d788ee84c1f9c3e9e393fc022d07a25424e5bd1e4bb423b497e3b04c879e1f

Tx prefix hash: 83da4124792e89c7e3d4a77ff37a81d5d4b9b199f261920eb0509a3baaf553c7
Tx public key: 52cb39f561d590bcb22b08e79a3ac683526bb83739aa1301bb03bdb0da7a300c
Timestamp: 1723799421 Timestamp [UCT]: 2024-08-16 09:10:21 Age [y:d:h:m:s]: 00:282:01:12:15
Block: 1089049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201506 RingCT/type: yes/0
Extra: 0152cb39f561d590bcb22b08e79a3ac683526bb83739aa1301bb03bdb0da7a300c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf64b3dc4d7aadf475083258452b604849f99d03aa8d8c5bea60d92e04b43e2b 0.600000000000 1563668 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": 1089059, "vin": [ { "gen": { "height": 1089049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf64b3dc4d7aadf475083258452b604849f99d03aa8d8c5bea60d92e04b43e2b" } } ], "extra": [ 1, 82, 203, 57, 245, 97, 213, 144, 188, 178, 43, 8, 231, 154, 58, 198, 131, 82, 107, 184, 55, 57, 170, 19, 1, 187, 3, 189, 176, 218, 122, 48, 12, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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