Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07f758ebcac8711cc5d21c614dd19fa486b7b02ca55e4c2acde44b65b54c3991

Tx prefix hash: 1d454762c90343f83f0d3e1d40c729ca04de490b7df60623c4db869c28d83d0c
Tx public key: 043fb3e0af5f9459cdc034589be34db7fa9d169df974461562e47c76a71ebe42
Timestamp: 1723659480 Timestamp [UCT]: 2024-08-14 18:18:00 Age [y:d:h:m:s]: 00:234:19:13:00
Block: 1087897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167674 RingCT/type: yes/0
Extra: 01043fb3e0af5f9459cdc034589be34db7fa9d169df974461562e47c76a71ebe4202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4413c8906e4386cab7d5e78aea8e1a55b5553cbf7c3faa1aaec73e53a8559ff4 0.600000000000 1562508 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": 1087907, "vin": [ { "gen": { "height": 1087897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4413c8906e4386cab7d5e78aea8e1a55b5553cbf7c3faa1aaec73e53a8559ff4" } } ], "extra": [ 1, 4, 63, 179, 224, 175, 95, 148, 89, 205, 192, 52, 88, 155, 227, 77, 183, 250, 157, 22, 157, 249, 116, 70, 21, 98, 228, 124, 118, 167, 30, 190, 66, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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