Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f5a82d87ea7b07a83f87992e345fbe47eb6a3f23b851ebfd41c628e86d72d45

Tx prefix hash: 56fb43d43a56be0bb08c35ebb6dd22a8f3fe5496f143269fd41cc8e061141169
Tx public key: 3f671a84923c0cd19aa2344a28a75fdd6ecc1d9805ad07a186a6b15344243778
Timestamp: 1715065709 Timestamp [UCT]: 2024-05-07 07:08:29 Age [y:d:h:m:s]: 00:337:02:12:00
Block: 1016654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240956 RingCT/type: yes/0
Extra: 013f671a84923c0cd19aa2344a28a75fdd6ecc1d9805ad07a186a6b1534424377802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4af739673c3a2750052ef1e4d0b3f421e755cb759669cdd8a3155adbfcf60d1 0.600000000000 1480299 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": 1016664, "vin": [ { "gen": { "height": 1016654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4af739673c3a2750052ef1e4d0b3f421e755cb759669cdd8a3155adbfcf60d1" } } ], "extra": [ 1, 63, 103, 26, 132, 146, 60, 12, 209, 154, 162, 52, 74, 40, 167, 95, 221, 110, 204, 29, 152, 5, 173, 7, 161, 134, 166, 177, 83, 68, 36, 55, 120, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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