Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4ff6212e16a584b399ecc87c26590417b246c2e68c81caf964043df88d74885

Tx prefix hash: 25de288853e11f7bb335e02b76ec4c9fa976106f7ab4dd599f89a53450bc3882
Tx public key: 34547616703fb333debd2592cb029d649153425c4c74dc1b6013eb45481d811c
Timestamp: 1713542855 Timestamp [UCT]: 2024-04-19 16:07:35 Age [y:d:h:m:s]: 01:198:23:55:44
Block: 1004017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400871 RingCT/type: yes/0
Extra: 0134547616703fb333debd2592cb029d649153425c4c74dc1b6013eb45481d811c021100000004e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fcf7e11b6f3dd0e4bdb1233dd061c5f669446d430b9d9e1455d13e1c23503e8 0.600000000000 1464577 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": 1004027, "vin": [ { "gen": { "height": 1004017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fcf7e11b6f3dd0e4bdb1233dd061c5f669446d430b9d9e1455d13e1c23503e8" } } ], "extra": [ 1, 52, 84, 118, 22, 112, 63, 179, 51, 222, 189, 37, 146, 203, 2, 157, 100, 145, 83, 66, 92, 76, 116, 220, 27, 96, 19, 235, 69, 72, 29, 129, 28, 2, 17, 0, 0, 0, 4, 228, 187, 107, 131, 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