Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c70582b88e19c8d3e65cda8b56d5082c44aaa84d524293085455a8a9de191ce

Tx prefix hash: 389e8b071e116b7349e31929545bbeb91d73f4f9cda2e7a4c15fc29cbf4a287c
Tx public key: 724e738c7f8ea3db6315f36c5fc1a9f74d8d7bd52e4adaa9cc89f3eb21cf559c
Timestamp: 1728658754 Timestamp [UCT]: 2024-10-11 14:59:14 Age [y:d:h:m:s]: 00:089:17:47:29
Block: 1129341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64144 RingCT/type: yes/0
Extra: 01724e738c7f8ea3db6315f36c5fc1a9f74d8d7bd52e4adaa9cc89f3eb21cf559c021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e2af4c902f72892eeb23fe8e48af93e11a2661d4c7ce7b65470ce36aab6d43c 0.600000000000 1612166 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": 1129351, "vin": [ { "gen": { "height": 1129341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e2af4c902f72892eeb23fe8e48af93e11a2661d4c7ce7b65470ce36aab6d43c" } } ], "extra": [ 1, 114, 78, 115, 140, 127, 142, 163, 219, 99, 21, 243, 108, 95, 193, 169, 247, 77, 141, 123, 213, 46, 74, 218, 169, 204, 137, 243, 235, 33, 207, 85, 156, 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