Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0fddb2716270c342e86e70e376f991e93d8299e74406086d919632484c881ff

Tx prefix hash: cd0f49c393c9006ef380bde26a8d8318106ac77517bdceabb394889f4ec62244
Tx public key: 63e9e989f21848557c3e7d08db18d7c6d3035bf550a2f111188f301e1e9bb46b
Timestamp: 1632663637 Timestamp [UCT]: 2021-09-26 13:40:37 Age [y:d:h:m:s]: 03:131:10:57:08
Block: 341247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870308 RingCT/type: yes/0
Extra: 0163e9e989f21848557c3e7d08db18d7c6d3035bf550a2f111188f301e1e9bb46b0211000000b1f60c5d7e000000000000000000

1 output(s) for total of 45.427100067000 dcy

stealth address amount amount idx
00: 4435b45c0bbcc950ba4e9e4da1d000a5d97aae70af0aa3f776eb4f7947d8e7b8 45.427100067000 701105 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": 341257, "vin": [ { "gen": { "height": 341247 } } ], "vout": [ { "amount": 45427100067, "target": { "key": "4435b45c0bbcc950ba4e9e4da1d000a5d97aae70af0aa3f776eb4f7947d8e7b8" } } ], "extra": [ 1, 99, 233, 233, 137, 242, 24, 72, 85, 124, 62, 125, 8, 219, 24, 215, 198, 211, 3, 91, 245, 80, 162, 241, 17, 24, 143, 48, 30, 30, 155, 180, 107, 2, 17, 0, 0, 0, 177, 246, 12, 93, 126, 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