Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe0721cbd15912892553b96ba393b1a617c8a4b0eccb74321399da10d4fe8e5a

Tx prefix hash: 8e81d3b0997f7e8ef9c4fd31cab32cf34db9824d2ce5c86223e3a83fea1d331f
Tx public key: 3a202f59e7188cbc2a522968f7de4a884901b3ec730e57f55eb130d20d94dc02
Timestamp: 1707099837 Timestamp [UCT]: 2024-02-05 02:23:57 Age [y:d:h:m:s]: 00:345:07:54:15
Block: 950587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247226 RingCT/type: yes/0
Extra: 013a202f59e7188cbc2a522968f7de4a884901b3ec730e57f55eb130d20d94dc020211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fa0f80f000a06717560a86081a04c2364bc1a3fd52b89141c81dbcaccd282f8 0.600000000000 1409227 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": 950597, "vin": [ { "gen": { "height": 950587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fa0f80f000a06717560a86081a04c2364bc1a3fd52b89141c81dbcaccd282f8" } } ], "extra": [ 1, 58, 32, 47, 89, 231, 24, 140, 188, 42, 82, 41, 104, 247, 222, 74, 136, 73, 1, 179, 236, 115, 14, 87, 245, 94, 177, 48, 210, 13, 148, 220, 2, 2, 17, 0, 0, 0, 2, 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