Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 894a06e1b383959074e7b061636a1c73462f07685b444af8de4423738bde0e60

Tx prefix hash: dd804339aa3626a2ca2e0758fb2b91aa6868f6a763f614ef0f6ac39041018fd8
Tx public key: d5860edbdbe068bc470d8be26f546caa5637bfaa0c438c8717eb0edb7aa4fa09
Timestamp: 1721627264 Timestamp [UCT]: 2024-07-22 05:47:44 Age [y:d:h:m:s]: 00:261:16:37:10
Block: 1071037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186951 RingCT/type: yes/0
Extra: 01d5860edbdbe068bc470d8be26f546caa5637bfaa0c438c8717eb0edb7aa4fa09021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a34a543f2511b1564e95a3267c6b9e00c9db3c44b60fb0ca459e7c9ca71a4bd2 0.600000000000 1543112 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": 1071047, "vin": [ { "gen": { "height": 1071037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a34a543f2511b1564e95a3267c6b9e00c9db3c44b60fb0ca459e7c9ca71a4bd2" } } ], "extra": [ 1, 213, 134, 14, 219, 219, 224, 104, 188, 71, 13, 139, 226, 111, 84, 108, 170, 86, 55, 191, 170, 12, 67, 140, 135, 23, 235, 14, 219, 122, 164, 250, 9, 2, 17, 0, 0, 0, 4, 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