Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae7f9229a3e4b857d59441c1f1ce3d6b41ad042039c68f6e4191697046175949

Tx prefix hash: 92fc704601f21fbe4928cacddb479a5ca3ce325236e5d3505b73ec47be26e0c4
Tx public key: 7b51a1bf21fef2b512a0e81f9252806f71d47e794fd0e02f5bdaec5ce4f74ff2
Timestamp: 1710039745 Timestamp [UCT]: 2024-03-10 03:02:25 Age [y:d:h:m:s]: 01:095:07:23:27
Block: 974990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329096 RingCT/type: yes/0
Extra: 017b51a1bf21fef2b512a0e81f9252806f71d47e794fd0e02f5bdaec5ce4f74ff20211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cc0918210206ef33b347d696a20409822908d33746d0fe4fd13d11fdc95c39a 0.600000000000 1434959 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": 975000, "vin": [ { "gen": { "height": 974990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cc0918210206ef33b347d696a20409822908d33746d0fe4fd13d11fdc95c39a" } } ], "extra": [ 1, 123, 81, 161, 191, 33, 254, 242, 181, 18, 160, 232, 31, 146, 82, 128, 111, 113, 212, 126, 121, 79, 208, 224, 47, 91, 218, 236, 92, 228, 247, 79, 242, 2, 17, 0, 0, 0, 5, 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