Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ba8882015ee9a83fc4749216471b9efb207ee747fe8a086ceb93c7b2a99f2c7

Tx prefix hash: a7f5766e8d4f99157bc501ac9ae8c62f2ac4fccd38dc42f41f46d5cfb1195452
Tx public key: d1f2ab5f68a4550dd3f876e64cef9fae443b3846e51e364d896c6203cf327b5d
Timestamp: 1700272382 Timestamp [UCT]: 2023-11-18 01:53:02 Age [y:d:h:m:s]: 01:141:16:43:41
Block: 894004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362436 RingCT/type: yes/0
Extra: 01d1f2ab5f68a4550dd3f876e64cef9fae443b3846e51e364d896c6203cf327b5d0211000000014b8f5122000000000000000000

1 output(s) for total of 0.669566353000 dcy

stealth address amount amount idx
00: 093a50209a9fbf6dfa24519bd7a637b6a48ad84c2bba0c26e612f8563f11e358 0.669566353000 1350191 of 0

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": 894014, "vin": [ { "gen": { "height": 894004 } } ], "vout": [ { "amount": 669566353, "target": { "key": "093a50209a9fbf6dfa24519bd7a637b6a48ad84c2bba0c26e612f8563f11e358" } } ], "extra": [ 1, 209, 242, 171, 95, 104, 164, 85, 13, 211, 248, 118, 230, 76, 239, 159, 174, 68, 59, 56, 70, 229, 30, 54, 77, 137, 108, 98, 3, 207, 50, 123, 93, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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