Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 691a5fb71fd7ae8a313049ef60dc6c7370ef6b034913f962b02e929b285a4045

Tx prefix hash: 2099c22d5c8e4fe6d36ad602b4672598230bdd2cb5f8935b0fbfe7205c5402b5
Tx public key: a40616ea4b33dd1cd2bd2707fb0e73864fe0f0bec06051b25d4c3acff5c4e8d6
Timestamp: 1720337173 Timestamp [UCT]: 2024-07-07 07:26:13 Age [y:d:h:m:s]: 01:147:12:27:56
Block: 1060353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363984 RingCT/type: yes/0
Extra: 01a40616ea4b33dd1cd2bd2707fb0e73864fe0f0bec06051b25d4c3acff5c4e8d602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b84b365dd0a38cd3df2f1d4086d381eb596c05f2cb45f21e6cea4cd9ede26f50 0.600000000000 1530830 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": 1060363, "vin": [ { "gen": { "height": 1060353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b84b365dd0a38cd3df2f1d4086d381eb596c05f2cb45f21e6cea4cd9ede26f50" } } ], "extra": [ 1, 164, 6, 22, 234, 75, 51, 221, 28, 210, 189, 39, 7, 251, 14, 115, 134, 79, 224, 240, 190, 192, 96, 81, 178, 93, 76, 58, 207, 245, 196, 232, 214, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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