Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 307c306d53d2f9e84bb97f988850e6320ea870d2c698d8a83435d62c542c7599

Tx prefix hash: 8a59adf729b19df629b7b11b0c509622214f5446429c262f99a8de5bb38bbd15
Tx public key: 7710a7756fdc55a60973e8db5721210b1a38939c58dd304fc96af7917a6d0d9b
Timestamp: 1728933995 Timestamp [UCT]: 2024-10-14 19:26:35 Age [y:d:h:m:s]: 00:210:23:02:43
Block: 1131629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150578 RingCT/type: yes/0
Extra: 017710a7756fdc55a60973e8db5721210b1a38939c58dd304fc96af7917a6d0d9b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e7570d071e5e7e8d8680bf110b64dccc51aa9423fedfd8ceb6b50617b24ae5d 0.600000000000 1614532 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": 1131639, "vin": [ { "gen": { "height": 1131629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e7570d071e5e7e8d8680bf110b64dccc51aa9423fedfd8ceb6b50617b24ae5d" } } ], "extra": [ 1, 119, 16, 167, 117, 111, 220, 85, 166, 9, 115, 232, 219, 87, 33, 33, 11, 26, 56, 147, 156, 88, 221, 48, 79, 201, 106, 247, 145, 122, 109, 13, 155, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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