Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7a98d4981ef29f5fb3f20f1932d7dcbb150ba4e640e260dfa591187a18fe149

Tx prefix hash: cda2d93da18fb099a9cdc72a80e5102d3caea67511f3c9719c2a698a80b4d8fa
Tx public key: 025b38df4e4102be394d6eaaaabc12bb9cc2e16324fcf17750afa4804a02c702
Timestamp: 1685906157 Timestamp [UCT]: 2023-06-04 19:15:57 Age [y:d:h:m:s]: 02:153:19:49:09
Block: 775142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 629718 RingCT/type: yes/0
Extra: 01025b38df4e4102be394d6eaaaabc12bb9cc2e16324fcf17750afa4804a02c702021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.658184853000 dcy

stealth address amount amount idx
00: 367f8b2b6aed7d911831ba8ae9a8d992ad9352f437a9257d9a479d690d4a83d9 1.658184853000 1224643 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": 775152, "vin": [ { "gen": { "height": 775142 } } ], "vout": [ { "amount": 1658184853, "target": { "key": "367f8b2b6aed7d911831ba8ae9a8d992ad9352f437a9257d9a479d690d4a83d9" } } ], "extra": [ 1, 2, 91, 56, 223, 78, 65, 2, 190, 57, 77, 110, 170, 170, 188, 18, 187, 156, 194, 225, 99, 36, 252, 241, 119, 80, 175, 164, 128, 74, 2, 199, 2, 2, 17, 0, 0, 0, 3, 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