Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f2cbf77521ab13954a54d7cd1e180d5476984675f071a35ad92a08e8efef2c

Tx prefix hash: 466a19e8dd53e5b390d17b33c5d9c2b4b277cc52e91fd8097176a45e7620e5a0
Tx public key: f06540f0e3468d835b07e5581d83387e488d2fb1c04d68a8493f18ec8a1d7e89
Timestamp: 1584303126 Timestamp [UCT]: 2020-03-15 20:12:06 Age [y:d:h:m:s]: 05:234:04:28:48
Block: 83516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1320911 RingCT/type: yes/0
Extra: 01f06540f0e3468d835b07e5581d83387e488d2fb1c04d68a8493f18ec8a1d7e89021100000001203e3db0000000000000000000

1 output(s) for total of 324.552616454000 dcy

stealth address amount amount idx
00: adaa1a651f16f69f1ea92f4e9b0a5d9b973a69f50db36d39a2a0bafe08bc3bed 324.552616454000 151810 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": 83526, "vin": [ { "gen": { "height": 83516 } } ], "vout": [ { "amount": 324552616454, "target": { "key": "adaa1a651f16f69f1ea92f4e9b0a5d9b973a69f50db36d39a2a0bafe08bc3bed" } } ], "extra": [ 1, 240, 101, 64, 240, 227, 70, 141, 131, 91, 7, 229, 88, 29, 131, 56, 126, 72, 141, 47, 177, 192, 77, 104, 168, 73, 63, 24, 236, 138, 29, 126, 137, 2, 17, 0, 0, 0, 1, 32, 62, 61, 176, 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