Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3d478f00f9495a83165c71b196b6423c18301fc69d6b0951f51c9d13f54c0d

Tx prefix hash: dd5b3f41b8aa00f789c3e6a05642090db04122b03a43cf1f6883eb94a608351d
Tx public key: 7a6c6db35fe5a46471351ecc6127d7a93b125fbf5ab0fb3172d28409592d16dc
Timestamp: 1727880381 Timestamp [UCT]: 2024-10-02 14:46:21 Age [y:d:h:m:s]: 00:261:01:05:44
Block: 1122895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186252 RingCT/type: yes/0
Extra: 017a6c6db35fe5a46471351ecc6127d7a93b125fbf5ab0fb3172d28409592d16dc02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa0b7c1b6751111412f8e66ca7b8274a5025d2b8fe558285be22aa4cd136b425 0.600000000000 1605428 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": 1122905, "vin": [ { "gen": { "height": 1122895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa0b7c1b6751111412f8e66ca7b8274a5025d2b8fe558285be22aa4cd136b425" } } ], "extra": [ 1, 122, 108, 109, 179, 95, 229, 164, 100, 113, 53, 30, 204, 97, 39, 215, 169, 59, 18, 95, 191, 90, 176, 251, 49, 114, 210, 132, 9, 89, 45, 22, 220, 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