Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2928447947f37fc7f010ffd94050a5938e19f9996b6d8e7e4e184dd65bbf1ac8

Tx prefix hash: f4a66fd0576367833f80af2fc0656ea750b86539a1b07558e8f7f95982246efa
Tx public key: 40f69bea6e74a8ca6e0df2dcacdd5e3779de3876ed094470f6b40b5f15805992
Timestamp: 1734189548 Timestamp [UCT]: 2024-12-14 15:19:08 Age [y:d:h:m:s]: 00:136:17:55:28
Block: 1175099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97553 RingCT/type: yes/0
Extra: 0140f69bea6e74a8ca6e0df2dcacdd5e3779de3876ed094470f6b40b5f158059920211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee49db5a0a8e11696a7113ae3fb20e6f645bb601f9eb393366828b0b42108093 0.600000000000 1661332 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": 1175109, "vin": [ { "gen": { "height": 1175099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee49db5a0a8e11696a7113ae3fb20e6f645bb601f9eb393366828b0b42108093" } } ], "extra": [ 1, 64, 246, 155, 234, 110, 116, 168, 202, 110, 13, 242, 220, 172, 221, 94, 55, 121, 222, 56, 118, 237, 9, 68, 112, 246, 180, 11, 95, 21, 128, 89, 146, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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