Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc6dcb1fa8b99aa58762424806307e4dc389bc183f2a4883b6d678ec7820fe60

Tx prefix hash: bbe503f7c0a47df0813ca9aded70e9b3ca1854ca00db2de892616b52c2596d44
Tx public key: 1f22d7ba46ea7667b1c24accb029775b14229ac318a0eb3d7fa79acbaa057b60
Timestamp: 1697580917 Timestamp [UCT]: 2023-10-17 22:15:17 Age [y:d:h:m:s]: 02:048:07:36:39
Block: 871889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554176 RingCT/type: yes/0
Extra: 011f22d7ba46ea7667b1c24accb029775b14229ac318a0eb3d7fa79acbaa057b60021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.792628765000 dcy

stealth address amount amount idx
00: 989fdae2bae47db2041c864dabdecb309fab8791a84e0c85192b2af84545d068 0.792628765000 1326924 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": 871899, "vin": [ { "gen": { "height": 871889 } } ], "vout": [ { "amount": 792628765, "target": { "key": "989fdae2bae47db2041c864dabdecb309fab8791a84e0c85192b2af84545d068" } } ], "extra": [ 1, 31, 34, 215, 186, 70, 234, 118, 103, 177, 194, 74, 204, 176, 41, 119, 91, 20, 34, 154, 195, 24, 160, 235, 61, 127, 167, 154, 203, 170, 5, 123, 96, 2, 17, 0, 0, 0, 5, 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