Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ed5e69f9f84fa1e877da4c80c584fb3bbbbd671a546387eeca2f16c71506d98

Tx prefix hash: 72a6026f7a8bdaaf47a2d09a57054f95b5038b2c01e36625ba8309abb35a52ac
Tx public key: a1764d08a14afb9cab4546a208e538696c9fdfdc1f605a869553a13328e85f6d
Timestamp: 1720884086 Timestamp [UCT]: 2024-07-13 15:21:26 Age [y:d:h:m:s]: 00:289:11:20:43
Block: 1064896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206831 RingCT/type: yes/0
Extra: 01a1764d08a14afb9cab4546a208e538696c9fdfdc1f605a869553a13328e85f6d02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42a14f30543ba8d803af4cf5b036ad184b611c8224d21107966a086f927cd994 0.600000000000 1535437 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": 1064906, "vin": [ { "gen": { "height": 1064896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42a14f30543ba8d803af4cf5b036ad184b611c8224d21107966a086f927cd994" } } ], "extra": [ 1, 161, 118, 77, 8, 161, 74, 251, 156, 171, 69, 70, 162, 8, 229, 56, 105, 108, 159, 223, 220, 31, 96, 90, 134, 149, 83, 161, 51, 40, 232, 95, 109, 2, 17, 0, 0, 0, 16, 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