Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba57eefe7d1c0679871c183258c0a14006b783d48f00c0eb76b08375eefee0e5

Tx prefix hash: 93c8cbaa7bc67957f2b2859b73610b42015bde9d4b89a37587b7c5a4b30d31fc
Tx public key: bb53405fe2579c3c170a336f8683661a22ba76d6505d9d8e507bf3fb05da2fff
Timestamp: 1736796037 Timestamp [UCT]: 2025-01-13 19:20:37 Age [y:d:h:m:s]: 00:156:12:39:12
Block: 1196657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111556 RingCT/type: yes/0
Extra: 01bb53405fe2579c3c170a336f8683661a22ba76d6505d9d8e507bf3fb05da2fff0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d573934d47a2f540d72d3ede7bc7b7a3fc62e4128f6bdc43785e19268fe6bb0 0.600000000000 1683258 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": 1196667, "vin": [ { "gen": { "height": 1196657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d573934d47a2f540d72d3ede7bc7b7a3fc62e4128f6bdc43785e19268fe6bb0" } } ], "extra": [ 1, 187, 83, 64, 95, 226, 87, 156, 60, 23, 10, 51, 111, 134, 131, 102, 26, 34, 186, 118, 214, 80, 93, 157, 142, 80, 123, 243, 251, 5, 218, 47, 255, 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