Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3e6b28009bbd6adfc84759a1875f38dab7e65400239d0daa6e1b1b38e09da5f

Tx prefix hash: a2b5745e5a476c4a99765f7728c2e7d1925362c74ff15503077dc15597b80900
Tx public key: 8ca8ba1f65b2ffc291700b6ff1931898688e15b30618b583bff869d43b5c74f6
Timestamp: 1711473992 Timestamp [UCT]: 2024-03-26 17:26:32 Age [y:d:h:m:s]: 01:047:23:40:01
Block: 986897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295267 RingCT/type: yes/0
Extra: 018ca8ba1f65b2ffc291700b6ff1931898688e15b30618b583bff869d43b5c74f60211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98c59ce2f2fddbeb4bbbe3d4d24b9151e98ed53989461a933f06fa2a1669d4c8 0.600000000000 1447134 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": 986907, "vin": [ { "gen": { "height": 986897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98c59ce2f2fddbeb4bbbe3d4d24b9151e98ed53989461a933f06fa2a1669d4c8" } } ], "extra": [ 1, 140, 168, 186, 31, 101, 178, 255, 194, 145, 112, 11, 111, 241, 147, 24, 152, 104, 142, 21, 179, 6, 24, 181, 131, 191, 248, 105, 212, 59, 92, 116, 246, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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