Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf960dd5b213808a47acf73a12c96a6c7a8bdf87625310f39defb321e674b32

Tx prefix hash: 55d0e1b6a85b15a66d972568fcdd5cef31ecc32c9b878eef5e7eae92d3dd076a
Tx public key: e3ee6bae830431c52d4432c9257190a8c853633873afa8a3c175e9ad4b1a8d5a
Timestamp: 1717339659 Timestamp [UCT]: 2024-06-02 14:47:39 Age [y:d:h:m:s]: 01:243:19:39:10
Block: 1035507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432760 RingCT/type: yes/0
Extra: 01e3ee6bae830431c52d4432c9257190a8c853633873afa8a3c175e9ad4b1a8d5a02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88bcbdd261c1f8db0c3e9f84f234a7d2066f4d3da4d68a0cc2ed8464c0584b52 0.600000000000 1504028 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": 1035517, "vin": [ { "gen": { "height": 1035507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88bcbdd261c1f8db0c3e9f84f234a7d2066f4d3da4d68a0cc2ed8464c0584b52" } } ], "extra": [ 1, 227, 238, 107, 174, 131, 4, 49, 197, 45, 68, 50, 201, 37, 113, 144, 168, 200, 83, 99, 56, 115, 175, 168, 163, 193, 117, 233, 173, 75, 26, 141, 90, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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