Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89a6930efd43c6b62c10381db033a43f0c704be097ea2d048cc645441641264d

Tx prefix hash: b3330c911d236e8d8a49eba6f176f84c308ba4c8060773fea6ebfce3c5c6f782
Tx public key: b0c4c78c1a3dde255314640e30b94436cfb8779707da5b7601d1e38db4b2b12e
Timestamp: 1696839777 Timestamp [UCT]: 2023-10-09 08:22:57 Age [y:d:h:m:s]: 01:177:04:42:51
Block: 865754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387668 RingCT/type: yes/0
Extra: 01b0c4c78c1a3dde255314640e30b94436cfb8779707da5b7601d1e38db4b2b12e021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.830610927000 dcy

stealth address amount amount idx
00: 8c9e68ab87dc42c5e4858e992690bfaeae267e8cbcebb251790c78afe892f1ae 0.830610927000 1320300 of 0

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": 865764, "vin": [ { "gen": { "height": 865754 } } ], "vout": [ { "amount": 830610927, "target": { "key": "8c9e68ab87dc42c5e4858e992690bfaeae267e8cbcebb251790c78afe892f1ae" } } ], "extra": [ 1, 176, 196, 199, 140, 26, 61, 222, 37, 83, 20, 100, 14, 48, 185, 68, 54, 207, 184, 119, 151, 7, 218, 91, 118, 1, 209, 227, 141, 180, 178, 177, 46, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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