Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30745750328ce81b1483d08fb7f5cc62e97cf2c4d92730bb1227ceccde72ed3b

Tx prefix hash: fb5c906736b2d254f0dac22f686fd8fb656ecd4869af909f0e90c9387c00f5b2
Tx public key: d76f2d00f8eaa5ae2eb7e889d93df0ddda77f3375f05a9d5cde81f77187bfe4f
Timestamp: 1725685664 Timestamp [UCT]: 2024-09-07 05:07:44 Age [y:d:h:m:s]: 00:208:15:54:23
Block: 1104689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148969 RingCT/type: yes/0
Extra: 01d76f2d00f8eaa5ae2eb7e889d93df0ddda77f3375f05a9d5cde81f77187bfe4f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c591e56baf2a61e9f6d780293b68564bba5f9ec65214a4bfb71b272de6809331 0.600000000000 1581928 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": 1104699, "vin": [ { "gen": { "height": 1104689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c591e56baf2a61e9f6d780293b68564bba5f9ec65214a4bfb71b272de6809331" } } ], "extra": [ 1, 215, 111, 45, 0, 248, 234, 165, 174, 46, 183, 232, 137, 217, 61, 240, 221, 218, 119, 243, 55, 95, 5, 169, 213, 205, 232, 31, 119, 24, 123, 254, 79, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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