Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe8ce0747d818d9974a1f4474b7980415eac5144eba2d1460b7d0c2a52d86ef

Tx prefix hash: 2f139e2eb9d6494f2bff0b50ff1b4fe3733795dc6c87eff7767867314338195d
Tx public key: fc3ec278e69926c984b38176e1389f9aec7702a5df9878d1b5de4ca148c55cc8
Timestamp: 1721976209 Timestamp [UCT]: 2024-07-26 06:43:29 Age [y:d:h:m:s]: 00:252:14:54:50
Block: 1073925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180464 RingCT/type: yes/0
Extra: 01fc3ec278e69926c984b38176e1389f9aec7702a5df9878d1b5de4ca148c55cc8021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 692fa4208617ac5bc57b1e84bd8e18c727dc337f909fc2227ac0fd1eda72cbf2 0.600000000000 1546434 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": 1073935, "vin": [ { "gen": { "height": 1073925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "692fa4208617ac5bc57b1e84bd8e18c727dc337f909fc2227ac0fd1eda72cbf2" } } ], "extra": [ 1, 252, 62, 194, 120, 230, 153, 38, 201, 132, 179, 129, 118, 225, 56, 159, 154, 236, 119, 2, 165, 223, 152, 120, 209, 181, 222, 76, 161, 72, 197, 92, 200, 2, 17, 0, 0, 0, 16, 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