Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45680847c9b99181cb525a8a9e01b2e2c64ef83e6aaa622e7975089c41e718fe

Tx prefix hash: 592e26f6215bc84d72f43c6cae15be0c7ffe42730f657b9713a4b72ca676e89a
Tx public key: cc652694939ae3ac25ff0873b322de8d7f0564e20df12c8efbe1bf1964e554ab
Timestamp: 1729013277 Timestamp [UCT]: 2024-10-15 17:27:57 Age [y:d:h:m:s]: 00:039:14:38:53
Block: 1132278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28278 RingCT/type: yes/0
Extra: 01cc652694939ae3ac25ff0873b322de8d7f0564e20df12c8efbe1bf1964e554ab021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69d44fb2acc0c5eb8b5e8630e6f3ab4ff3fc12321a3f15c19c827bbce9cef19a 0.600000000000 1615191 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": 1132288, "vin": [ { "gen": { "height": 1132278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69d44fb2acc0c5eb8b5e8630e6f3ab4ff3fc12321a3f15c19c827bbce9cef19a" } } ], "extra": [ 1, 204, 101, 38, 148, 147, 154, 227, 172, 37, 255, 8, 115, 179, 34, 222, 141, 127, 5, 100, 226, 13, 241, 44, 142, 251, 225, 191, 25, 100, 229, 84, 171, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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