Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 688d9458a0406bea8bde1c3194ab3350e1775870890f117684eaa182febdb874

Tx prefix hash: 6afc51e5bf52f7a11a850f076f4a68f821022c20da8d05f080a416eca6e55878
Tx public key: b84d77dce9d4a17ec0a6aacb94dcdadbc84c4f94b6ab9f2bfddfb274377e2f70
Timestamp: 1727579127 Timestamp [UCT]: 2024-09-29 03:05:27 Age [y:d:h:m:s]: 00:055:23:34:27
Block: 1120393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40006 RingCT/type: yes/0
Extra: 01b84d77dce9d4a17ec0a6aacb94dcdadbc84c4f94b6ab9f2bfddfb274377e2f70021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28a68a64edb31119fc577ff32e96dcb2cd1c5514ccc6a03dbd3da7c414aaf171 0.600000000000 1602292 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": 1120403, "vin": [ { "gen": { "height": 1120393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28a68a64edb31119fc577ff32e96dcb2cd1c5514ccc6a03dbd3da7c414aaf171" } } ], "extra": [ 1, 184, 77, 119, 220, 233, 212, 161, 126, 192, 166, 170, 203, 148, 220, 218, 219, 200, 76, 79, 148, 182, 171, 159, 43, 253, 223, 178, 116, 55, 126, 47, 112, 2, 17, 0, 0, 0, 3, 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