Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95c822bb9c96ef3b74c2ac55bd65f5069c4623991f05b8156bdaf923886b1af

Tx prefix hash: 1ff595ef5486eab84e64c7864ecf79cb18140e8826149af19745a7797afba2e8
Tx public key: 80725fd6a44ee68b7de843533929fb4f7c14a14a721efe898b7a1e9f8d6b0c38
Timestamp: 1734029468 Timestamp [UCT]: 2024-12-12 18:51:08 Age [y:d:h:m:s]: 00:322:19:59:52
Block: 1173781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228215 RingCT/type: yes/0
Extra: 0180725fd6a44ee68b7de843533929fb4f7c14a14a721efe898b7a1e9f8d6b0c38021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02fe487f0aa3065798d02ab0c39bb1da713c02c6eced969b7048d869fc02cbde 0.600000000000 1659842 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": 1173791, "vin": [ { "gen": { "height": 1173781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02fe487f0aa3065798d02ab0c39bb1da713c02c6eced969b7048d869fc02cbde" } } ], "extra": [ 1, 128, 114, 95, 214, 164, 78, 230, 139, 125, 232, 67, 83, 57, 41, 251, 79, 124, 20, 161, 74, 114, 30, 254, 137, 139, 122, 30, 159, 141, 107, 12, 56, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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