Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3402d30188e8d51df1ff4e791801ba60adab1ae4ccbfddc170eb466e84a8b953

Tx prefix hash: b7bbf8e7c92b1d7ec58c2170fc7bcfe4877b060c8e5eac44256ee1e9c5e43309
Tx public key: 4754482eade9ee6423e9a33191c5954a20ceef60324f9262d84a77e9b12f0a96
Timestamp: 1728630421 Timestamp [UCT]: 2024-10-11 07:07:01 Age [y:d:h:m:s]: 00:243:20:31:13
Block: 1129107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174077 RingCT/type: yes/0
Extra: 014754482eade9ee6423e9a33191c5954a20ceef60324f9262d84a77e9b12f0a9602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d7103525392c586156299bf2b2decb08b735f4c4bc8728c8debde6c333dea2c 0.600000000000 1611932 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": 1129117, "vin": [ { "gen": { "height": 1129107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d7103525392c586156299bf2b2decb08b735f4c4bc8728c8debde6c333dea2c" } } ], "extra": [ 1, 71, 84, 72, 46, 173, 233, 238, 100, 35, 233, 163, 49, 145, 197, 149, 74, 32, 206, 239, 96, 50, 79, 146, 98, 216, 74, 119, 233, 177, 47, 10, 150, 2, 17, 0, 0, 0, 6, 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