Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51cd2adf10ecb00e5953a58af17edc03391d78776a1a5849728c30d3cd9d8011

Tx prefix hash: 9876ac853ebf39f729f8abd91b3acda7810d6895ba44379f2e94341a558972f9
Tx public key: afd839f1cf30e550c27f4a95862ba530ac60e563300a0bee417a71d865fc7cf1
Timestamp: 1687109765 Timestamp [UCT]: 2023-06-18 17:36:05 Age [y:d:h:m:s]: 01:253:20:16:38
Block: 785135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442561 RingCT/type: yes/0
Extra: 01afd839f1cf30e550c27f4a95862ba530ac60e563300a0bee417a71d865fc7cf1021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.536462523000 dcy

stealth address amount amount idx
00: e3249825ede1668d08c61c4c7e35132b793ff13f72a3512e4ed3eaa0a92b442a 1.536462523000 1235068 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": 785145, "vin": [ { "gen": { "height": 785135 } } ], "vout": [ { "amount": 1536462523, "target": { "key": "e3249825ede1668d08c61c4c7e35132b793ff13f72a3512e4ed3eaa0a92b442a" } } ], "extra": [ 1, 175, 216, 57, 241, 207, 48, 229, 80, 194, 127, 74, 149, 134, 43, 165, 48, 172, 96, 229, 99, 48, 10, 11, 238, 65, 122, 113, 216, 101, 252, 124, 241, 2, 17, 0, 0, 0, 4, 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