Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffad9326c112969357bfd2025ec87cd0d6fd0d1a9528392b6e311ac1b47a806d

Tx prefix hash: 977cb3d29e5a3a3399b8cf465457edab0419e3ef24ba09416659dc466f7a1430
Tx public key: 6a3a0541579e4fa8aa90ca7d37abab6085d8e5608fb07a211d40bfa948037014
Timestamp: 1715570274 Timestamp [UCT]: 2024-05-13 03:17:54 Age [y:d:h:m:s]: 00:201:03:28:46
Block: 1020854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143952 RingCT/type: yes/0
Extra: 016a3a0541579e4fa8aa90ca7d37abab6085d8e5608fb07a211d40bfa948037014021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ff8d54daf5a0e7f1ef0bb40799b2f1bfb83b71e10ce71241e77616e2ae179f8 0.600000000000 1484967 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": 1020864, "vin": [ { "gen": { "height": 1020854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ff8d54daf5a0e7f1ef0bb40799b2f1bfb83b71e10ce71241e77616e2ae179f8" } } ], "extra": [ 1, 106, 58, 5, 65, 87, 158, 79, 168, 170, 144, 202, 125, 55, 171, 171, 96, 133, 216, 229, 96, 143, 176, 122, 33, 29, 64, 191, 169, 72, 3, 112, 20, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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