Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbb27c0d4e8fb9e3aaa3c0a7f80eb0167ccb87e580e84aa1908ba89c2840227e

Tx prefix hash: 36124bfa7397a5516ef3f76d99f41edaaf4b1e4981c0694f98ceaa137fc800b0
Tx public key: a7a231637a44f5aa8114f3c954c359131e184b2d498b071ce2af76372c2f5556
Timestamp: 1712059753 Timestamp [UCT]: 2024-04-02 12:09:13 Age [y:d:h:m:s]: 00:240:08:01:19
Block: 991700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172076 RingCT/type: yes/0
Extra: 01a7a231637a44f5aa8114f3c954c359131e184b2d498b071ce2af76372c2f555602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7ada723024bae443d3c1c8662e662e0e33eeaf85749daa0b14749f07de1dd27 0.600000000000 1452036 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": 991710, "vin": [ { "gen": { "height": 991700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7ada723024bae443d3c1c8662e662e0e33eeaf85749daa0b14749f07de1dd27" } } ], "extra": [ 1, 167, 162, 49, 99, 122, 68, 245, 170, 129, 20, 243, 201, 84, 195, 89, 19, 30, 24, 75, 45, 73, 139, 7, 28, 226, 175, 118, 55, 44, 47, 85, 86, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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